AWS Lambda End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all AWS Lambda versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
AWS Lambda Java 8 (AL2023) is supported until August 31, 2029, its end-of-support date. Active support for AWS Lambda Java 8 (AL2023) ends on June 30, 2029; security fixes continue until that end-of-life date. The next AWS Lambda version to reach end of life is .NET 8, on March 3, 2027. 16 of 52 tracked AWS Lambda versions are past end of life; the most recent to reach it, .NET Core 3.1, did so on May 3, 2023. The full AWS Lambda lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Node.js 0.10 | — | Nov 13, 2014 | Oct 31, 2016 | 3611 days past EOL | EOL |
| Java 8 (AL1) | — | Jun 15, 2015 | Mar 3, 2027 | 164 days remaining | Warning |
| Python 2.7 | — | Oct 8, 2015 | May 30, 2022 | 1574 days past EOL | EOL |
| Node.js 4.3 | — | Apr 7, 2016 | Mar 5, 2020 | 2390 days past EOL | EOL |
| .NET Core 1.0 | — | Dec 1, 2016 | Jul 30, 2019 | 2609 days past EOL | EOL |
| Node.js 6.10 | — | Mar 22, 2017 | Aug 12, 2019 | 2596 days past EOL | EOL |
| Python 3.6 | — | Apr 18, 2017 | Aug 29, 2022 | 1483 days past EOL | EOL |
| Node.js 4.3 edge | — | Jul 17, 2017 | Apr 30, 2019 | 2700 days past EOL | EOL |
| Go 1.x | — | Jan 15, 2018 | Mar 3, 2027 | 164 days remaining | Warning |
| .NET Core 2.0 | — | Jan 15, 2018 | May 30, 2019 | 2670 days past EOL | EOL |
| Node.js 8.10 | — | Apr 2, 2018 | Mar 6, 2020 | 2389 days past EOL | EOL |
| .NET Core 2.1 | — | Jul 9, 2018 | Apr 13, 2022 | 1621 days past EOL | EOL |
| Python 3.7 | — | Nov 19, 2018 | Mar 3, 2027 | 164 days remaining | Warning |
| Custom Runtime (AL1) | — | Nov 29, 2018 | Mar 3, 2027 | 164 days remaining | Warning |
| Ruby 2.5 | — | Nov 29, 2018 | Mar 31, 2022 | 1634 days past EOL | EOL |
| Node.js 10 | — | May 15, 2019 | Feb 14, 2022 | 1679 days past EOL | EOL |
| Java 11 | — | Nov 18, 2019 | Aug 31, 2027 | 345 days remaining | Active |
| Python 3.8 | — | Nov 18, 2019 | Mar 3, 2027 | 164 days remaining | Warning |
| Node.js 12 | — | Nov 18, 2019 | Apr 30, 2023 | 1239 days past EOL | EOL |
| Ruby 2.7 | — | Feb 19, 2020 | Mar 3, 2027 | 164 days remaining | Warning |
| .NET Core 3.1 | — | Mar 31, 2020 | May 3, 2023 | 1236 days past EOL | EOL |
| Custom Runtime (AL2) | — | Aug 12, 2020 | Mar 3, 2027 | 164 days remaining | Warning |
| Java 8 (AL2) | — | Aug 12, 2020 | Aug 31, 2027 | 345 days remaining | Active |
| .NET 5 (container-only) | — | Dec 2, 2020 | Not published | Past EOL | EOL |
| Node.js 14 | — | Feb 3, 2021 | Mar 3, 2027 | 164 days remaining | Warning |
| Python 3.9 | — | Aug 16, 2021 | Mar 3, 2027 | 164 days remaining | Warning |
| .NET 6 | — | Feb 24, 2022 | Mar 3, 2027 | 164 days remaining | Warning |
| Node.js 16 | — | May 12, 2022 | Mar 3, 2027 | 164 days remaining | Warning |
| .NET 7 (container-only) | — | Nov 15, 2022 | Not published | Past EOL | EOL |
| Node.js 18 | — | Nov 18, 2022 | Mar 3, 2027 | 164 days remaining | Warning |
| Python 3.10 | — | Apr 18, 2023 | Mar 3, 2027 | 164 days remaining | Warning |
| Java 17 | — | Apr 27, 2023 | Aug 31, 2027 | 345 days remaining | Active |
| Ruby 3.2 | — | Jun 7, 2023 | Mar 3, 2027 | 164 days remaining | Warning |
| Python 3.11 | — | Jul 27, 2023 | Aug 31, 2027 | 345 days remaining | Active |
| Custom Runtime (AL2023) | — | Nov 10, 2023 | Aug 31, 2029 | 1076 days remaining | Active |
| Node.js 20 | — | Nov 15, 2023 | Mar 3, 2027 | 164 days remaining | Warning |
| Java 21 | — | Nov 17, 2023 | Aug 31, 2029 | 1076 days remaining | Active |
| Python 3.12 | — | Dec 14, 2023 | Jan 10, 2029 | 843 days remaining | Active |
| .NET 8 | — | Feb 22, 2024 | Mar 3, 2027 | 164 days remaining | Warning |
| Ruby 3.3 | — | Apr 4, 2024 | May 31, 2027 | 253 days remaining | Active |
| Python 3.13 | — | Nov 14, 2024 | Aug 31, 2029 | 1076 days remaining | Active |
| Node.js 22 | — | Nov 22, 2024 | Jul 1, 2027 | 284 days remaining | Active |
| .NET 9 (container only) | — | Dec 9, 2024 | TBD | Supported | Active |
| Ruby 3.4 | — | Mar 27, 2025 | May 31, 2028 | 619 days remaining | Active |
| Java 25 | — | Nov 14, 2025 | Aug 31, 2029 | 1076 days remaining | Active |
| Python 3.14 | — | Nov 18, 2025 | Aug 31, 2029 | 1076 days remaining | Active |
| Node.js 24 | — | Nov 25, 2025 | Jul 1, 2028 | 650 days remaining | Active |
| .NET 10 | — | Jan 8, 2026 | Jan 15, 2029 | 848 days remaining | Active |
| Ruby 4.0 | — | Apr 30, 2026 | May 31, 2029 | 984 days remaining | Active |
| Java 8 (AL2023) | — | Jul 31, 2026 | Aug 31, 2029 | 1076 days remaining | Active |
| Java 11 (AL2023) | — | Jul 31, 2026 | Aug 31, 2029 | 1076 days remaining | Active |
| Java 17 (AL2023) | — | Jul 31, 2026 | Aug 31, 2029 | 1076 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/aws-lambda)
AWS Lambda release and support pattern
Of the 52 release lines tracked, 16 are past end of life and 36 are still within support; 2 are marked end of life without a published date. The newest line, java17.al2023, was released July 31, 2026. The next scheduled end of life is dotnet8 on March 3, 2027 — 163 days from this build. The longest-supported line currently published is provided.al2023, to August 31, 2029.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does AWS Lambda end of life mean for your organization?
When a version of AWS Lambda reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL AWS Lambda should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when AWS Lambda reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL AWS Lambda versions. This is a bridge, not a permanent solution — plan your migration in parallel.
AWS Lambda has 16 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for AWS Lambda is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."